PolicyStat Data Collection on Usage, Likeability, and Ease of Use in Large Orgs

#1

Hi everyone :wave:

We’re a large organization using PolicyStat, and we’re starting to look more intentionally at user experience and adoption.

I’d love to learn how other large orgs (10,000+ employees) are approaching this and collecting data from team members. Specifically:

  • How are you tracking whether users like PolicyStat?
  • Are you measuring ease of use or user satisfaction in a structured way (e.g., surveys, feedback loops, analytics)?
  • Do you collect feedback from specific user groups (frontline staff, leaders, policy owners, approvers)?
  • Have you found any metrics, questions, or approaches especially helpful in telling a meaningful story to leadership?

We’re hoping to move beyond anecdotal feedback and better understand what’s working well vs. where users may be struggling.

Any insights, examples, or lessons learned would be greatly appreciated—thank you!

#2

Hi @amalee.r. Thank you for posting this! Our product team is interested in hearing from anyone that has had success (or failures) with this. Maybe there is something we can do to help support in this area.

#3

Thank you Gabriel! Unfortunately the post has not gained too much traction.

I was thinking a pop-up box asking users to submit a survey on their experience could be a great way to solicit feedback for a larger organization like ours. In a perfect world, that survey could then be connected to the PolicyStatistics dashboard to present user feedback to site admins and executive leadership.

#4

We are new to PolicyStat and not yet live in the system. But would love to hear of ideas to collect feedback from our end users on what’s working, what’s not working, and where help is needed. We conducted some voice of customer surveys with high yield users in our old system. We had a standard set of questions, and each spent about an hour with different stakeholders soliciting their feedback. We found it to be a very valuable use of our time.

1 Like
#5

Leah, that is a great idea! How did you guys send out these surveys? Was there any incentive to completing the surveys? We have tried to send out MS Form Surveys but it can be tough to get people to participate…

#6

Hi Leah,

I did something similar at our multifacility organization. While I did not send out a survey, I emailed all policy owners by departments and those with elevated permissions that performed create/edit tasks. Then I met with their departments individually to give a high-level overview of what to expect with the migration to PolicyStat, including its limitations, as well as instructions for them to get their policies prepared for me to migrate when the time came. Some prep included ensuring correct ownership, retiring any policy that was no longer needed, and ensuring any policy they wanted migrated had a status of “Active” in the policy management system we were on at that time. Since our old system had sub-folder capability (Areas within Areas), but PolicyStat is only capable of having single-level Areas, I worked with departments to understand their needs so that I could set up Area structures that would best meet their needs. During those meetings, we also discussed elevated permissions and electronic approval workflows. By including each department in the process, we were well prepared for go-live, and it was successful.

#7

@enessa.whitten, thank you for sharing your process. Do you mind sharing how large your organization is?

I joined the organization team after PolicyStat was already implemented and the organization has now had the product for about 1.5 years. We are at the point where we want feedback on how people are liking the product after the initial implementation, what is working, what is not, etc.

If we were to rely on input from our policy owners, it may not be very reliable given we have about 300 policy owners and 13,000+ team members.

#8

Hi @amalee.r, I’ve sent you a message in the HUB with my email address. Please feel free to reach out.